Add Argo CD database migration mode - #21
Draft
yianni wants to merge 1 commit into
Draft
Conversation
yianni
changed the title
yianni
changed the title
yianni
changed the title
yianni
marked this pull request as ready for review
August 26, 2026 18:18
yianni
marked this pull request as draft
August 26, 2026 18:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add an optional Argo CD migration mode. It runs one ordinary Job in wave
1, then deploys Redash in wave2. The Job uses the existing/app/manage.py db upgradecommand.The default mode keeps the current Helm install and upgrade hooks unchanged.
This is the second migration slice and follows Terracode #9098. Applications that share the database must be synced one at a time.
Validation
3.0.16.No production resources were changed.